pages: add sections about local support for bindings in wrangler.toml#12731
pages: add sections about local support for bindings in wrangler.toml#12731admah merged 3 commits intoproductionfrom
Conversation
…l to d1, r2, kv, and service bindings docs
|
Files with changes (up to 15)
|
|
Pages using It seems a little strange to me to encourage this behaviour until Pages actually has full support for configuration in some capacity. |
|
@Cherry the goal of adding this would be to clear up that confusion for users by stating explicitly what is supported now. We are working towards support for Pages file-based configuration so we're not going to remove what is currently exposed. As we work towards that, we are also using this functionality to support better framework development like in |
|
I left a comment on the Especially if folks are going to have to update their configs again when Pages does support configuration. |
content/pages/functions/bindings.md
Outdated
|
|
||
| {{<Aside type="note">}} | ||
|
|
||
| `wrangler.toml` is currently **only** used for local development. Bindings specified in it are not available remotely. |
Just to make sure I understand, is the plan to support |
|
I think it would be extremely beneficial to hold this PR until it's made very clear in This is made especially and even more confusing when these new docs talk about Pages, link to wrangler configuration docs that detail how this does work when deploying (the linked docs pages are tailored for Workers), but then doesn't and no warnings are presented to the user. Most users struggle to understand the nuances between Workers and Pages right now, and I personally think this only adds to the confusion. |
… recommendation for remote bindings
Updated local bindings sections for: kv, r2, d1, and service bindings since those are currently supported.